Current Issue : January - March Volume : 2015 Issue Number : 1 Articles : 5 Articles
Introduction: In organizations with software systems in production, new and often\nunexpected requirements for development come up due to strategic, tactical, and\noperational customer needs. In this context, it is a strategic advantage for software\nsuppliers to be able to provide software services that meet these demands faster\nand with less overhead than negotiating traditional value-neutral project-oriented\nsoftware deliveries.\nCase description: This article reports on the industrial experience of restructuring the\nsupplier-side software development process into a value-based service-oriented format,\nguided by a service reference model. A service level agreement (SLA) was established\nbetween supplier and customer reflecting the business needs and values. The report\ndescribes the contractual aspects and internal managerial controls employed to facilitate\nthe compliance of the provided services with the SLA, including the integrated use of a\nmanagerial spreadsheet, an issue-tracking system, and a Kanban chart.\nDiscussion and evaluation: The feasibility and results of restructuring software\ndevelopment into a service-oriented format are evaluated. Major results were that\nonly moderate effort was required, around one person month, due to the support\nof the service reference model and a sufficient level of previously installed capabilities,\nand that the goals regarding improved quality, productivity, and customer satisfaction\nwere successfully achieved. Additionally we discuss stakeholder needs, the support\nfrom the service reference model, the lessons learned, and the success factors for\nsuch restructuring.\nConclusions: Restructuring software development in the format of continuous service\ndelivery, guided by a service reference model, is feasible and for suitable contexts can\nprovide significant benefits concerning quality, productivity, and customer satisfaction....
In this paper, we discussed the role of Free/Libre/Open Source Software (FLOSS) projects in computer science education and promote the use of this technology in education field. This paper discusses these projects and their benefits for student learning and examines the possibilities opened up by pursuing an open source philosophy also it explores the pros and cons of the FLOSS projects. The core requirement in the academia is to involve the students in FLOSS projects....
The scope and responsibilities of control applications are increasing due to, for example, the emergence of industrial internet. To\nmeet the challenge, model-driven development techniques have been in active research in the application domain. Simulations\nthat have been traditionally used in the domain, however, have not yet been sufficiently integrated to model-driven control\napplication development. In this paper, a model-driven development process that includes support for design-time simulations\nis complemented with support for simulating sequential control functions. The approach is implemented with open source tools\nand demonstrated by creating and simulating a control system model in closed-loop with a large and complex model of a paper\nindustry process....
Data from the Personal Software Process (PSP) courses indicate that the PSP improves the quality of the developed programs.\nHowever, since the programs (exercises of the course) are in the same application domain, the improvement could be due to\nprogramming repetition. In this research we try to eliminate this threat to validity in order to confirm that the quality improvement\nis due to the PSP. In a previous study we designed and performed a controlled experiment with software engineering undergraduate\nstudents at the Universidad de la Rep�´ublica. The students performed the same exercises of the PSP course but without applying the\nPSP techniques. Here we present a replication of this experiment. The results indicate that the PSP and not programming repetition\nis the most plausible cause of the important software quality improvements....
Background: Software reference architectures are becoming widely adopted by\norganizations that need to support the design and maintenance of software\napplications of a shared domain. For organizations that plan to adopt this\narchitecture-centric approach, it becomes fundamental to know the return on\ninvestment and to understand how software reference architectures are designed,\nmaintained, and used. Unfortunately, there is little evidence-based support to help\norganizations with these challenges.\nMethods: We have conducted action research in an industry-academia collaboration\nbetween the GESSI research group and everis, a multinational IT consulting firm based\nin Spain.\nResults: The results from such collaboration are being packaged in order to create\nguidelines that could be used in similar contexts as the one of everis. The main result of\nthis paper is the construction of empirically-grounded guidelines that support\norganizations to decide on the adoption of software reference architectures and to\ngather evidence to improve RA-related practices.\nConclusions: The created guidelines could be used by other organizations outside of\nour industry-academia collaboration. With this goal in mind, we describe the guidelines\nin detail for their use....
Loading....